Skip to content

Conversation

@tarcieri
Copy link
Member

Initial support for decoding BoxedUint from a byte slice.

Decoding is fallible and paramaterized around an expected precision. Requiring a known precision at decode time allows the caller to ensure that all values are the same dynamically-determined size so as to prevent subsequent timing variability with respect to input sizes.

Decoding is currently constrained to inputs that are multiples of the word size.

Initial support for decoding `BoxedUint` from a byte slice.

Decoding is fallible and paramaterized around an expected precision.
Requiring a known precision at decode time allows the caller to ensure
that all values are the same dynamically-determined size so as to
prevent subsequent timing variability with respect to input sizes.

Decoding is currently constrained to inputs that are multiples of the
word size.
@tarcieri tarcieri merged commit 65f45a4 into master Nov 25, 2023
@tarcieri tarcieri deleted the boxed-uint/decoding-functions branch November 25, 2023 20:31
@tarcieri tarcieri mentioned this pull request Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants